[https://nvbugs/6490049][test] Unwaive GB300 Kimi disagg e2e - #16920
[https://nvbugs/6490049][test] Unwaive GB300 Kimi disagg e2e#16920chienchunhung wants to merge 13 commits into
Conversation
|
/bot run --disable-fail-fast --stage-list "GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-2,GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-4" |
|
PR_Github #62031 [ run ] triggered by Bot. Commit: |
|
/bot run --disable-fail-fast --stage-list "GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-2,GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-4" |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds duration-balanced pytest-split performance test selection. The submit flow reuses the selected test for configuration and output naming. Generation-log synchronization now has a dedicated timeout and applies metric collection only to ChangesPytest-split performance selection
Generation-log synchronization
Performance waiver management
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant SubmitScript
participant PytestCommand
participant DurationData
participant ShardSelector
SubmitScript->>PytestCommand: Parse split options
SubmitScript->>DurationData: Load test durations
DurationData-->>ShardSelector: Provide test durations
PytestCommand-->>ShardSelector: Provide split and group values
ShardSelector-->>SubmitScript: Return one selected test
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot help |
GitHub Bot Help
Provide a user friendly way for developers to interact with a Jenkins server. Run See details below for each supported subcommand. Details
Launch build/test pipelines. All previously running jobs will be killed.
kill
Kill all running builds associated with pull request. skip
Skip testing for latest commit on pull request. reuse-pipeline
Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break. |
|
/bot kill |
|
PR_Github #62033 [ kill ] triggered by Bot. Commit: |
|
PR_Github #62031 [ run ] completed with state |
|
PR_Github #62033 [ kill ] completed with state |
BowenFu
left a comment
There was a problem hiding this comment.
Test-only: perf-sanity YAML gains kv_transfer_timeout_ms: 600000 (matching the equivalent GB200 Kimi config) and the two matching waivers come out. No product source, no default change — kv_transfer_timeout_ms is an existing per-config knob and the global 60s default is untouched. The single YAML serves both the e2e and gen_only variants, so both unwaived cases are covered.
Two notes, neither blocking:
- The targeted GB300 stages were aborted rather than green, so the e2e case (waived under the broader nvbugs/6490049) isn't yet proven to pass for this reason alone.
- #16921 removes the same
disagg_upload-e2e-gb300_kimi-...con4096...waiver line, so whichever lands second will need a rebase.
|
/bot run --disable-fail-fast --stage-list "GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-2,GB300-20_GPUs-5_Nodes-PyTorch-Disagg-PerfSanity-CTX1-NODE1-GPU4-GEN1-NODE4-GPU16-Post-Merge-4" |
|
/bot run --disable-fail-fast |
|
PR_Github #63513 [ run ] triggered by Bot. Commit: |
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
83ab4dc to
47846e9
Compare
|
/bot run --disable-fail-fast |
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
47846e9 to
cbd1a5e
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #63518 [ run ] triggered by Bot. Commit: |
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
…meout Signed-off-by: Chien-Chun Hung <2679986+chienchunhung@users.noreply.github.com>
|
PR_Github #63513 [ run ] completed with state |
cbd1a5e to
e4f6185
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #63520 [ run ] triggered by Bot. Commit: |
|
PR_Github #63518 [ run ] completed with state |
|
PR_Github #63527 [ run ] triggered by Bot. Commit: |
|
PR_Github #63520 [ run ] completed with state |
|
PR_Github #63527 [ run ] completed with state
|
tburt-nv
left a comment
There was a problem hiding this comment.
I'm not familiar with the perf sanity code paths, I'll defer to other reviewers in the qa review group.
Summary
e2eperf-sanity case tracked by NVBUG 6490049kv_transfer_timeout_ms=60000; this PR has no net timeout overridegen_onlycase unchanged; that case is tracked separately by NVBUG 6487038Why
mainstill skips this exacte2ecase under NVBUG 6490049. The correspondinggen_onlycase was already unwaived onmainby #16717, so it is not part of this PR's waiver diff.This PR was originally opened during the NVBUG 6487038 investigation. After rebasing onto the changes from #16717 and #16832, the remaining net waiver change is specifically the
e2ecase owned by NVBUG 6490049. The PR is therefore retargeted to that bug.Stack
e2e, where the GEN-only device-step-time metric is not collectedThe verification below was collected on the earlier patch-equivalent combined stack at commit
e0bfe69c484e2986528bca0ec6dfab1632d263c2. The current restacked head ise4f6185c312a30b2e5dad03c0efce1e4c30263f5;git range-diffconfirms all three #16920-specific commits are unchanged.Verification status
COMPLETE: every test unwaived by this PR has an exact targeted pass (1/1).
perf/test_perf_sanity.py::test_e2e[disagg_upload-e2e-gb300_kimi-k25-thinking-fp4_8k1k_con4096_ctx1_dep4_gen1_dep16_eplb0_mtp0_ccb-NIXL]perf/test_perf_sanity.py::test_e2e[disagg_upload-gen_only-gb300_kimi-k25-thinking-fp4_8k1k_con4096_ctx1_dep4_gen1_dep16_eplb0_mtp0_ccb-NIXL]The e2e run reported
1 passed, 2 skipped, 4153 deselected; its test call duration was1941.99sand pytest total was1951.11s. The GEN-only run also completed pytest and Slurm teardown successfully.The YAML has no explicit GEN or CTX
kv_transfer_timeout_msoverride, so both validations use the Python transceiver's existing 60-second default.QA-weekly scope
This PR does not unwaive a QA-weekly test. The weekly lists already contain the Kimi concurrency-4096 NIXL and UCX
disagg-e2eentries withoutSKIPmarkers. They are distinct from the post-mergedisagg_upload-e2enode unwaived here.The QA local launcher receives one exact
--test-listnode ID and writes a one-entry test list. It therefore has no pytest-split shard-selection mismatch to mirror from #17134's CI-launcher fix.Scope
The PR removes one
e2ewaiver. It does not change the global KV-transfer timeout, add a GB300 timeout override, modify the inherited GEN-only waiver state, or add/remove a QA-weekly waiver.